Password problems in MS NetMeeting

Helpline Q&A Directory

I use Microsoft NetMeeting version 3.01. When I set up Remote desktop sharing it asks for a password to be set for access. After this it works fine and I'm able to access my PC's desktop from my laptop. However if I reboot my PC, when I try to access the desktop remotely, my password is no longer accepted and I can't change it back as the request for the old password is rejected too.

I phoned Microsoft support who, after some head scratching, suggested I delete a folder in the Registry. This deleted the password and allowed me to set a new one. However, to my dismay and annoyance, I later discovered it also deleted all my passwords. Since the problem recurs this is not acceptable. Can you help?

This sounds like a known problem that can occur when NetBios for the TCP/IP protocol is not enabled and the TCP connection is not active. To resolve it you should do the following.

First, uninstall NetMeeting using Control Panel, Add/Remove Programs. If the Client for Microsoft Networks is not installed, you should now install it using the following steps. Open Control Panel, Network. Select the Configuration tab, click Add, Client, Add, and select Microsoft in the Manufacturers box. Select Client for Microsoft Networks in the Network Clients box, then click ok twice. Insert the Windows 98 CD-ROM when requested, and click Yes when prompted to restart the computer.

If Client for Microsoft Networks is installed you should enable NetBios for TCP/IP by performing the following steps. Open Control Panel, Network, select the Configuration tab. Click TCP/IP and then Properties. In the TCP/IP Properties dialog box, click NetBios, select 'I want to enable NetBios over TCP/IP', then click ok twice. If you receive the message 'Your network is not complete. Do you want to continue?' select Yes.

Make sure that the TCP connection is active (you are connected to the internet or your local network) and then reinstall NetMeeting. Installing the latest version of NetMeeting (version 4.4.3388 or later) may also resolve this problem.